Context

This PR adds a new property called titlePath to TestResult and makes Allure NUnit, Allure xUnit.net, Allure SpecFlow, and Allure.Reqnroll fill it.

More about titlePath: allure-framework/allure-js#1260.

NUnit

For an NUnit test, the titlePath follows the NUnit ITest hierarchy. Only nodes at the TestSuite level or higher are translated into titlePath.

Example:

Given a test assembly called MyTestAssembly and the following code:

using NUnit.Framework;

namespace Foo.Bar;

class Baz
{
    [Test]
    public void Qux() { }

    [TestCase(1)]
    public void Qut(int _) { }
}

The titlePath of both tests will be as follows:

[
  "MyTestAssembly", // the assembly name
  "Foo",  // the namespace
  "Bar", // the namespace
  "Baz", // the test class
]

The test class part can be renamed from code via the TestFixture.TestName property.

xUnit.net

For xUnit.net tests, the titlePath is defined by the tests' declaring type (a test class). It contains the assembly name, namespace elements, and the class name.

Reqnroll and SpecFlow

For Reqnroll and SpecFlow tests, the titlePath contains the assembly name, the parent directories of the feature file inside the assembly, and the feature name. If the feature is nameless, the Feature placeholder is used instead.

Checklist

• Sign Allure CLA
• Provide unit tests